How to prepare Management System to work on Microsoft Windows 2003

Technology Support

  1. Open Computer Management:
    [Start] -> Run... -> compmgmt.msc -> [OK]
  2. Select Your web site :
    Computer Management (local) -> Services and Applications ->Internet Inforamtion Services -> Web Sites -> Web Site Name
  3. Open Properties:
    Action -> Properties
  4. New window with Web Site Properties will open.
    Select [Home Directory] tab and click [Configuration...] button.
  5. Application Configuration Window will open.
    Select [App Mappings] Tab

Please make sure that web server supports files with these extensions (configuration for Microsoft .NET Framework 2.0):

Note: You can Remove DEBUG option on Live System.

Make sure that you are allowing web services to use GET and POST protocols

Open /web.config file (located on the root folder of website) and make sure that you have these lines. These lines will allow Web Services of website to use GET and POST protocols:

<system.web>
    <!-- PROTOCOLS FOR WEBSERVICES
    Allow webservices to use these protocols on web server.
    -->
    <webServices>
        <protocols>
            <add name="HttpGet"/>
            <add name="HttpPost"/>
        </protocols>
    </webServices>


Problem:

ASP pages returns errors: HTTP Error 404 - File or directory not found.

Solution:

  1. You need to enable ASP Support. Open Computer Management:
    [Start] -> Run... -> compmgmt.msc -> [OK]
  2. Select Internet Information Service:
    Computer Management (local) -> Services and Applications ->Internet Inforamtion Services -> Web Service Extensions
  3. On right side select "Active Server pages" and press [Allow] button.

 

Problem:

First of all some pages of Management System will try to send large amount of data to client side. This can result in error with message "Response Buffer Limit Exceeded". Also posting of large files can result in "ASP 0101: Operation Not Allowed" error message.

Solution:

  1. Open Computer Management:
    [Start] -> Run... -> compmgmt.msc -> [OK]
  2. Select Internet Information Service:
    Computer Management (local) -> Services and Applications ->Internet Inforamtion Services.
  3. Open Properties:
    Action -> Properties
  4. New window with IIS Properties will open. Check option:
    [x] E nable Direct Metabase Edit -> [OK]

To Download very large files from server:

  1. Open metabase configuration file:
    [Start] -> Run... -> notepad %SystemRoot%\system32\inetsrv\Metabase.xml -> [OK]
  2. Find parameter "AspBufferingLimit":
    CTRL+F -> AspBufferingLimit -> [Find Next]
  3. Change the AspBufferingLimit setting to a larger size. The default value is 4194304, which is 4 MB. You can change value to 67108864, which is 64 MB. This change does not require stopping IIS.
  4. Save and close file.

To Upload very large files to server:

  1. Open metabase configuration file:
    [Start] -> Run... -> notepad %SystemRoot%\system32\inetsrv\Metabase.xml -> [OK]
  2. Find parameter "AspMaxRequestEntityAllowed":
    CTRL+F -> AspMaxRequestEntityAllowed -> [Find Next]
  3. Change the AspMaxRequestEntityAllowed setting to a larger size. The default value is 204800, which is 200 KB. You can change value to 16777216, which is 16 MB. This change does not require stopping IIS
  4. Save and close file.

Problem:

The Include file '../FileName.asp' cannot contain '..' to indicate the parent directory.

Solution:

  1. Open Computer Management:
    [Start] -> Run... -> compmgmt.msc -> [OK]
  2. Select Your web site :
    Computer Management (local) -> Services and Applications ->Internet Inforamtion Services -> Web Sites -> Web Site Name
  3. Open Properties:
    Action -> Properties
  4. New window with Web Site Properties will open.
    Select [Home Directory] tab and click [Configuration...] button.
  5. Application Configuration Window will open.
    Select [Options] Tab and check-in
    [x] Enable parent paths -> [OK] -> OK

 

Problem:

WebServices returns "HTTP/1.1 404 Object Not Found" error message.

Solution:

  1. Open Computer Management:
    [Start] -> Run... -> compmgmt.msc -> [OK]
  2. Select Your web site :
    Computer Management (local) -> Services and Applications ->Internet Inforamtion Services -> Web Sites -> Web Site Name
  3. Open Properties:
    Action -> Properties
  4. New window with Web Site Properties will open.
    Select [Home Directory] tab and click [Configuration...] button.
  5. Application Configuration Window will open.
    Select [App Mappings] Tab
  6. Select file with ".asmx" extension and click [Edit] button.
  7. Uncheck "Check that file exists checkbox:

 Problem:

Slow download speed

Solution:

Add support for restatting data transfers

Open: [Start] -> Control Panel -> Add or Remove Programs

  1. Select [Add/Remove Windos Components] on left side
  2. Select: Application Server -> [Details...] -> Internet Infomration Services (IIS) -> [Details...]
    Background Intelligent Transfer Services (BITS) Server Extensions

Compress files between client and server

  1. Open Computer Management:
    [Start] -> Run... -> compmgmt.msc -> [OK]
  2. Select :
    Computer Management (local) -> Services and Applications ->Internet Inforamtion Services -> Web Sites
  3. Open from Menu: Action -> Properties.
  4. Select: [Service] tab.
  5. Click on:
    [x] Compress static files
    [x] Compress application files
Install QoS Packet Scheduler
  1. From the Start menu, point to Settings, and then click Network and Dial-up Connections.
  2. Click the Local Area Connection on which you want to install QoS Packet Scheduler, and then on the File menu, click Properties.
  3. Click Install, click Service, and then click Add.
  4. Click QoS Packet Scheduler, and then click OK.
  5. Click Close twice.

    Note   It is not necessary to restart the computer after installing Packet Scheduler.

Restart IIS

  1. [Start] -> Run... -> iisreset -> [OK]

 

How to Debug an ASP Project with Visual Studio .NET

One of our readers sent in this tip on how to get classic ASP debugging working from within Visual Studio .NET.

It took me a while to figure out how to enable debugging on a traditional ASP project with Visual Studio .NET using Windows 2000. I would always get an error saying:

"Unable to find project on the web server. Unable to set web server into correct debugging state automatically. You may not be able to debug .ASP pages."

After a lot of online research and fiddling with the settings, this is what worked for me.

To enable .asp debugging change the following settings:

  1. In VS.NET:
        project - properties
            configuration properties
                debugging
                    - enable ASP debugging
                    - enable ASP.NET debugging

  2. In the IIS snap-in:
        default website - properties
            home directory tab
                configuration
                    app debugging
                        - enable ASP server-side script debugging

        website (the project you want to debug) - properties
            directory tab
                application name: add
                    (this sets an application name for the website and changes the icon from a default folder icon to a website icon)

  3. Add IIS process account to Debugger Users group:
        In Computer Management snap-in:
            System Tools
                Local Users and Groups
                    Groups
                        Debugger Users - properties
                            Add user IWAM_machine-name (the "Launch IIS process account")

Now, to debug in VS.NET:

  1. Right-click the .asp page that the application should start from and select "Set as Start Page"
  2. Set a breakpoint in the .asp code anywhere in the project
  3. Click Debug -> Start or press F5 to build the project and start debugging

 

Also: Error occurs when the targeted Web server is configured with multiple virtual servers that are assigned the same IP address and same port number. The Visual InterDev 6.0 debugger binds to the virtual server using only the IP address and port number and ignores all other information, such as the Host Header Name. If the project that you are trying to debug is on the second virtual server, the debugger is unable to find the project because it binds to the first virtual server where the project does not exist. Thus, the error message occurs. Also, this error occurs when using Visual InterDev 6.0 to debug locally or remotely


Problem:

When instaling Role Security into Database with:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe
you are getting error: Setup failed. Exception: An error occurred during the execution of the SQL file 'InstallRoles.sql'. The SQL error number is 446 and the SqlException message is: Cannot resolve collation conflict for equal to operation. Cannot resolve collation conflict for equal to operation.

Solution:

  1. In most cases it means that Collation of your SQL Server:
    Youc an check this with SQL Command:  SELECT serverproperty('collation')
    or from SQL Server Properties [General] tab.
    does not mach Collation of your database:
    Youc an check this from SQL Server -> Databases -> DatabaseName > Properties -> [General] Tab
    Note: In most cases this happens after import of database from another server.
    Note: You can list available collations with command: SELECT * FROM ::fn_helpcollations()
  2. Rebuild Master database (not recommanded if database collation is old):
  3. Shutdown Microsoft® SQL Server™ 2000
  4. Run: %ProgramFiles%\Microsoft SQL Server\80\Tools\Binn\Rebuildm.exe
  5. In the Rebuild Master dialog box, click Browse.
  6. In the Browse for Folder dialog box, select the \Data folder on the SQL Server 2000 compact disc or in the shared network directory from which SQL Server 2000 was installed, and then click OK.
  7. Click Settings. In the Collation Settings dialog box, verify or change settings used for the master database and all other databases.
  8. Initially, the default collation settings are shown, but these may not match the collation selected during setup. You can select the same settings used during setup or select new collation settings. When done, click OK.
  9. In the Rebuild Master dialog box, click Rebuild to start the process.

    The Rebuild Master utility reinstalls the master database.

    Note  To continue, you may need to stop a server that is running.